Open
Conversation
Read /proc/self/fd to report the actual number of open file descriptors alongside the existing limit. Comparing usage vs limit helps diagnose "too many open files" errors.
sbernauer
approved these changes
Apr 7, 2026
Member
sbernauer
left a comment
sbernauer
left a comment
There was a problem hiding this comment.
Yeah, it looks silly, but I couldn't find a better alternative
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
open_files_countfield to resources, read from/proc/self/fd- I checked but this seems to be the best way of getting that number. It seems a bit stupid to me counting this but....Nonegracefully if/proc/self/fdis unavailable even though I believe it should always be availableTest plan
cargo test --all-featurespassescargo clippywithRUSTFLAGS="-D warnings"passes